Device based network notification of device supported machine-type communication features

ABSTRACT

The disclosed subject matter provides a proactive device initiated mechanism for notifying a network device regarding device supported machine-type communication (MTC) features. In one embodiment, a method is provided that includes identifying, by a device comprising a processor, machine-type communication related parameters of the device using a subscriber identity module application stored on a subscriber identity module card of the device. The method can further include generating, by the device using the subscriber identity module application, parameter information that identifies the machine-type communication related parameters of the device based on the identifying, and sending, by the device, the parameter information to a network server device of a wireless communication network based on the generating.

TECHNICAL FIELD

The disclosed subject matter relates to techniques for providing devicebased network notification of device supported machine-typecommunication (MTC) features.

BACKGROUND

Machine-type communication (MTC) or machine-to-machine communication(M2M) refers to automated data communications among devices and theunderlying data transport infrastructure. The data communications mayoccur between an MTC device and a server, or directly between two MTCdevices. MTC has great potential in a wide range of applications andservices that are widespread across different industries, includinghealthcare, logistics, manufacturing, process automation, energy, andutilities. To spread these applications widely, cellular systems areconsidered as a potential candidate to provide connectivity for MTCdevices. However, the potential MTC applications have very differentfeatures and requirements, which imply constraints on the cellularnetwork technology as well as on MTC devices. As a result, differenttypes of MTC devices and different MTC device operating features arebeing developed and implemented to satisfy the diverse devicerequirements while balancing overall network service provisioningquality and efficiency. In order to manage MTC service provisioningeffectively, the network is informed of the different MTC features andfunctionalities of the MTC devices serviced by the network. However,current mechanisms for determining capabilities of user equipments (UEs)serviced by cellular network systems are not suitable for collectingdevice capability information for MTC devices.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is an illustration of an example wireless communication systemthat facilitates device based network notification of device supportedMTC features in accordance with various aspects and embodiments of thesubject disclosure.

FIG. 2 presents example network devices that facilitate providingwireless communication services to the UEs in accordance with variousaspects and embodiments of the subject disclosure.

FIG. 3 is an illustration of an example UE that facilitates device basednetwork notification of device MTC features in accordance with variousaspects and embodiments of the subject disclosure.

FIG. 4 provides a chart illustrating example MTC device type/categoryinformation in accordance with various aspects and embodiments of thesubject disclosure.

FIG. 5 presents example MTC device operating features in accordance withvarious aspects and embodiments of the subject disclosure.

FIG. 6 illustrates an example method that facilitates device basednetwork notification of device supported MTC features in accordance withvarious aspects and embodiments of the subject disclosure.

FIG. 7 illustrates another example method that device based networknotification of device supported MTC features in accordance with variousaspects and embodiments of the subject disclosure.

FIG. 8 illustrates another example method that device based networknotification of device supported MTC features in accordance with variousaspects and embodiments of the subject disclosure.

FIG. 9 depicts an example schematic block diagram of a computingenvironment with which the disclosed subject matter can interact.

FIG. 10 illustrates an example block diagram of a computing systemoperable to execute the disclosed systems and methods in accordance withan embodiment.

DETAILED DESCRIPTION

In current cellular network systems (e.g., third generation partnershipproject systems (3GPP) and the like), UE capability information issignaled to a terminating point in a number of ways depending on thetype of the capability information and the features and functionalitiesof the UE. For example, between the universal integrated circuit card(UICC) or the subscriber identity module (SIM) card and the UE, somedevice capability information is communicated via an informationdownload procedure referred to a “terminal profile download” procedure.Other device capability information is communicated between the UE andthe network via a UE capability information message (e.g., referred toas a “Classmark capability message” in 3GGP systems) sent by the UE viaan over-the-air (OTA) interface.

The different mechanisms via which UE capability information iscurrently provided to a terminating point however are limited in whatinformation can be conveyed and how it can be used. For example, thecapability information associated with the terminal profile downloadprocedure only describes SIM application toolkit (STK) or cardapplication toolkit (CAT) based device information so that an STK/CATapplication on the SIM or UICC knows what the device supports and canpossibly adjust its behavior accordingly. The information associatedwith the terminal profile download procedure does not contain anynon-STK based information, such as information regarding radiocapabilities of the device. On the other hand, although a UE capabilityinformation message can be used to transfer UE radio access capabilitiessuch as supported radio access technology (RAT), frequency bands, andsupported radio/network, this type of UE capability information is onlyreceived by the network in response to a direct request for theinformation from the network. For example, in order for the network toreceive such UE capability information, the network must send the UE aUE “capability enquiry message” (e.g., a reactive procedure as opposedto a proactive procedure). Additionally, the particular network devicethat receives the UE capability information in response to a capabilityenquiry message does not provide the UE capability information to othernetwork elements that may need the capability information to facilitatenew MTC related services associated with the UEs (e.g., provisioningsystems and billing systems).

The subject disclosure is directed to computer processing systems,computer-implemented methods, apparatus and/or computer program productsthat facilitate device based network notification of device supportedMTC features. In particular, the subject disclosure defines a proactivemechanism that can be used by a UE to convey certain key MTC devicecapability information to a network server device, referred to herein atthe “device capability collection server,” (DCCS). The DCCS can furtherprovide the MTC device capability information to other network serversand core network devices, such as network servers and core networkdevices associated with network billing and service provisioningsystems. These other network servers and core network devices canfurther use the MTC device capability information to facilitateprovisioning MTC services to MTC devices and/or to enable, disable,track, update, reconfigure, etc., MTC related device capabilities.

In one or more embodiments, a method is provided that includesidentifying, by a device comprising a processor, MTC related parametersof the device using a subscriber identity module application stored on asubscriber identity module card of the device. The method furtherincludes generating, by the device using the subscriber identity moduleapplication, MTC parameter information that identifies the MTC relatedparameters of the device based on the identifying, and sending, by thedevice, the MTC parameter information to a network server device of awireless communication network based on the generating.

In another embodiment, a device is provided that includes a transmitterand an integrated circuit (IC) card. In one implementation, the IC cardis a SIM card. In another implementation, the IC card is a UICC. The ICcard can comprise a processor, and a memory that stores executableinstructions that, when executed by the processor, facilitateperformance of various operations. These operations can include,determining MTC related parameters of the device, and generating MTCparameter information that identifies the MTC related parameters of thedevice based on the determining. These operations can further include,directing, based on the generating, the transmitter to send the MTCparameter information to a network server device of a wirelesscommunication network via a communication link between the device and anaccess point device of the wireless communication network.

In yet another embodiment, a machine-readable storage medium isprovided, comprising executable instructions that, when executed by aprocessor of a device, facilitate performance of operations. Theseoperations can include identifying MTC related parameters of the deviceusing a device capability information application stored on a universalintegrated circuit card of the device. The operations can furtherinclude generating, using the device capability information application,MTC parameter information that identifies the MTC related parameters ofthe device based on the identifying; and, sending the MTC parameterinformation to a network server device of a wireless communicationnetwork based on the generating.

The subject disclosure is now described with reference to the drawings,wherein like reference numerals are used to refer to like elementsthroughout. The following description and the annexed drawings set forthin detail certain illustrative aspects of the subject matter. However,these aspects are indicative of but a few of the various ways in whichthe principles of the subject matter can be employed. Other aspects,advantages, and novel features of the disclosed subject matter willbecome apparent from the following detailed description when consideredin conjunction with the provided drawings. In the following description,for purposes of explanation, numerous specific details are set forth inorder to provide a thorough understanding of the subject disclosure. Itmay be evident, however, that the subject disclosure may be practicedwithout these specific details. In other instances, well-knownstructures and devices are shown in block diagram form in order tofacilitate describing the subject disclosure.

FIG. 1 is an illustration of an example wireless communication system100 that facilitates device based network notification of devicesupported MTC features in accordance with various aspects andembodiments of the subject disclosure. Aspects of the systems,apparatuses or processes explained in this disclosure can constitutemachine-executable component(s) embodied within machine(s), e.g.,embodied in one or more computer readable mediums (or media) associatedwith one or more machines. Such component(s), when executed by the oneor more machines, e.g., computer(s), computing device(s), virtualmachine(s), etc. can cause the machine(s) to perform the operationsdescribed.

The wireless communication system 100 can be or include various types ofdisparate networks, including but not limited to: cellular networks,femto networks, picocell networks, microcell networks, internet protocol(IP) networks Wi-Fi service networks, broadband service network,enterprise networks, cloud based networks, and the like. System 100 cancomprise one or more UEs 102, a network node 104 and a core wirelesscommunication network 106. It should be appreciated that four UEs (UEs102 ₁₋₄) are merely arbitrarily depicted for exemplary purposes and thatany number N UEs can be included in system 100. The UEs 102 can includea variety of different mobile and stationary device types, including butnot limited to: a cellular phone, a smartphone, a tablet computer, awearable device, a virtual reality (VR) device, a heads-up display (HUD)device, and the like. In various exemplary embodiments, the UEs 102 canbe configured with MTC or M2M capabilities. For example, the UEs 102 canbe or include metering devices, implantable medical device (IMDs),sensor and/or control devices associated with home automation systems,tracking devices, point of sale devices (e.g., vending, machines),security devices (e.g., associated with surveillance systems, homessecurity, access control, etc.), and the like. The terms MTC and M2M areused herein interchanged. A UE that is configured to perform one or moreMTC functionalities is referred to herein as an MTC device.

In some implementations, the UEs 102 can be configured to communicatewith one another using a machine-to-machine (M2M) link (indicated by thedashed arrow lines). For example, in the embodiment shown, UEs 102 ₁ and102 ₂ have established an M2M link and UEs 102 ₂ and 102 ₃ have alsoestablished an M2M link. One or more of the UEs 102 can further beconfigured to communicate with a core wireless communication network 106(i.e., one or more network devices 108 of the core wirelesscommunication network 106) using a communication link establishedbetween the UE 102 and a network node 104 of the wireless communicationnetwork (e.g., indicated by the thin dashed arrow lines). Acommunication link between a UE and a network access point device suchas network node 104 is referred to herein as machine-to-network (M2N)communication link. For example, in the embodiment shown, UEs 102 ₂ andUE 102 ₄ have established M2N wireless communication links with thenetwork node 104. In some implementations, a UE 102 can serve as anaccess point device to other UEs via which the other UEs can communicatewith the network node 104. For example, in the embodiment shown, UE 102₂ serves as a network access point device for UEs 102 ₁ and 102 ₃.

The wireless communication system 100 can employ various wirelesscommunication technologies and modulation schemes to facilitate wirelessradio communications between devices (e.g., between UEs 102 and betweenUEs 102 and the network node 104). For example, the UEs 102 can beconfigured to communicate with the network node 104 and/or one anotherusing various wireless communication technologies, including but notlimited to: Universal Mobile Telecommunications System (UMTS)technologies, Long Term Evolution (LTE) technologies, advanced LTEtechnologies (including voice over LTE or VoLTE), Code Division MultipleAccess (CDMA) technologies, Time Division Multiple Access (TDMA)technologies, Orthogonal Frequency Division Multiplexing (OFDN)technologies, Filter Bank Multicarrier (FBMC) technologies, WirelessFidelity (Wi-Fi) technologies, Worldwide Interoperability for MicrowaveAccess (WiMAX) technologies, General Packet Radio Service (GPRS)technologies, Enhanced GPRS, technologies, Third Generation PartnershipProject (3GPP) technologies, Fourth Generation Partnership Project(4GPP) technologies, Fifth Generation Partnership Project (5GPP)technologies, Ultra Mobile Broadband (UMB) technologies, High SpeedPacket Access (HSPA) technologies, Evolved High Speed Packet Access(HSPA+), High-Speed Downlink Packet Access (HSDPA) technologies,High-Speed Uplink Packet Access (HSUPA) technologies, ZIGBEE®technologies, or another IEEE 802.XX technology. Additionally,substantially all aspects disclosed herein can be exploited in legacytelecommunication technologies. In some embodiments, the UEs can beconfigured to communicate with one another (e.g., via M2M links) usingsuitable local area network (LAN) or personal area network (PAN)communication technologies and configured to communicate with thenetwork node 104 using suitable WAN communication technologies. Forexample, in one or more embodiments, the UEs 102 can be configured tocommunicate with one another using BLUETOOTH®, BLUETOOTH® low energy(BLE), near field communication (NFC), Wi-Fi protocol, ZIGBEE®, RF4CE,WirelessHART, 6LoWPAN, Z-Wave, ANT, and the like. The one or more UEs102 can be further configured to communicate with the network node 104using one or more of the radio access network (RAN) technologies listedabove (e.g., LTE, VoLTE, UMTS, etc.).

The non-limiting term network node (or radio network node) is usedherein to refer to any type of network node serving a UE 102 and/orconnected to other network node, network element, or another networknode from which the UE 102 can receive a radio signal. Examples ofnetwork nodes (e.g., network node 104) can include but are not limitedto: NodeB devices, base station (BS) devices, access point (AP) devices,and radio access network (RAN) devices. The network node 104 can alsoinclude multi-standard radio (MSR) radio node devices, including but notlimited to: an MSR BS, an eNode B, a network controller, a radio networkcontroller (RNC), a base station controller (BSC), a relay, a donor nodecontrolling relay, a base transceiver station (BTS), a transmissionpoint, a transmission nodes, an RRU, an RRH, nodes in distributedantenna system (DAS), and the like.

The core wireless communication network 106 can include various networkdevices 108 that facilitate providing wireless communication services tothe UEs 102 via the network node 104 and/or various additional networkdevices (not shown). For example, the network devices 108 of the corenetwork can include mobile switching center (MSCs) devices, a homelocation register (HLR) device, a visitor location register (VLR)device, authentication center (AUC) devices, provisioning servers,billing servers, operation and support system (OSS) devices, shortmessage service center (SMSC) devices, and many other elements. In oneor more exemplary embodiments in which the UEs 102 are or include MTCdevices, the network devices 108 can include one or more network devicesthat facilitate various MTC services supported by the respective UEs 102(e.g., the DCCS, MTC application servers, and other elements). Thenetwork node 104 connects the UEs to the core wireless communicationnetwork 106. The network node can be connected to the core wirelesscommunication network via one or more backhaul links (indicated by thethick arrow line). For example, the one or more backhaul links caninclude wired link components, such as but not limited to: like a T1/E1phone line, a digital subscriber line (DSL) (e.g., either synchronous orasynchronous), an asymmetric DSL (ADSL), an optical fiber backbone, acoaxial cable, and the like. The one or more backhaul links can alsoinclude wireless link components, such as but not limited to,line-of-sight (LOS) or non-LOS links which can include terrestrialair-interfaces or deep space links (e.g., satellite communication linksfor navigation).

The subject disclosure provides a mechanism for automaticallycollecting, by the core wireless communication network 106, MTCcapability information about the UEs 102 serviced by the wirelesscommunication network. In particular, in one or more embodiments, theUEs 102 of system 100 can be configured to determine defined MTCcapability information in response to start-up (i.e., powering on), inresponse to a reset procedure, or another defined event. For example, inresponse to start-up, each of the UEs 102 can be configured to identifyor determine information including a defined MTC device type or categoryof the UE and defined MTC related features supported or not supported bythe UE. The UEs 102 can further be configured to automatically sendtheir MTC capability information to a specific network device of thecore wireless communication network 106 in association withestablishment of an M2N connection between the UE and a network node(e.g., network node 104). This network device is referred to herein asthe device capability collection server (DCCS). The DCCS can furtherstore the MTC device capability information in a database accessible toother network devices of the core wireless communication network and/orprovide the MTC device capability information to the other networkdevices to facilitate managing various MTC related operations of theUEs.

The specific parts of the MTC capability information that are employedby the other network devices and/or the manner in which the MTCcapability information is employed by the other network devices canvary. For example, in some implementations, the MTC capabilityinformation can be employed by one or more provisioning servers of thewireless communication network to facilitate provisioning MTC servicesfor the respective UEs. In telecommunication, provisioning involves theprocess of preparing and equipping the network to allow it to provide(new) services to its UEs. Accordingly, using MTC capability informationfor a UE, a provisioning server of the wireless communication networkcan configure any required network elements to provide the UE with MTCservices supported by a UE in accordance with business logic andresource management operations employed by the wireless communicationnetwork. Thus in some implementations, a provisioning server of the corewireless communication network 106 can employ MTC device capabilityinformation to enable and/or disable different MTC services provided bythe wireless communication network to the MTC device. In anotherexample, the MTC capability information can be employed by a billingserver of the wireless communication network to facilitate charging auser account associated with a UE in accordance with the servicesprovisioned for the UE based on the MTC capabilities of the UE. Otherpossible uses of device MTC capability information can include UEtracking, controlling MTC operations of the UE, controlling non MTCoperations of the UE that have an effect on the MTC operations of theUE, and adjusting operating parameters associated with MTC featuressupported by the UE.

For example, FIG. 2 presents some example network devices 200 of awireless communication that facilitate providing wireless communicationservices to the UEs by the wireless communication network in accordancewith various aspects and embodiments of the subject disclosure. Invarious embodiments, the one or more of the network devices 108 ofsystem 100 can be or include one or more of the network devices 200.Repetitive description of like elements employed in respectiveembodiments is omitted for sake of brevity.

As shown in FIG. 2, the network devices 200 can include but are notlimited to: a packet data network gateway (PWG) server 202, a servicegateway (SGW) server 204, a mobility management entity (MME) server 206,a home subscriber server (HSS) 208, service capability server (SCS) 212,a MTC-interworking function (MTC-IWF) server 214, a provisioning server216, a billing/records server 218 and a DCCS 220. The PGW and the SGWare responsible for forwarding UE data traffic to and from the networkvia the so-called bearers, (i.e. channels created with the end users).The MME is responsible for all mobility related functions, paging,authentication, and bearer management in the network. The HSS functionsas a main database containing subscription-related information. The SCSentity is designed to offer services for MTC applications hosted inexternal networks. The MTC-IWF hides the internal public land mobilenetwork (PLMN) topology and relays or translates signaling protocols toinvoke specific functionalities in PLMN. This entity is also responsiblefor relaying trigger requests from the SCS after checking authorizationand reporting the acceptance or denial of these requests. Theprovisioning server 216 is responsible for provision services for UEs,including MTC services and the billing/records server 218 is responsiblefor billing user accounts associated with the UEs in association withservices provisioned and utilized by the respective UEs, including MTCservices.

The DCCS is configured to automatically receive UE MTC capabilityinformation sent by respective UEs (e.g., UEs 102). The DCCS can furtherstore the UE MTC capability information in a database that is accessibleto one or more other core network devices (e.g., the a packet datanetwork gateway (PWG) server 202, the service gateway (SGW) server 204,the mobility management entity (MME) server 206, the home subscriberserver (HSS) 208, service capability server (SCS) 212, theMTC-interworking function (MTC-IWF) server 214, the provisioning server216, and the billing/records server 218). In some implementations, theDCCS can be configured to automatically provide the UE MTC capabilityinformation, or defined parts of the UE MTC capability information, toone or more other network devices of the network devices 200. In someembodiments, the DCCS can be or include an international mobileequipment identity (IMEI) trigger platform or ITP. For example, in someexisting cellular systems, the ITP has been responsible for maintainingdevice information for devices serviced by the network. This deviceinformation has included device IMEI numbers, terminal profileinformation, and device location information. The mechanisms via whichthe different types of device information are received by the ITP vary.In some implementations, the ITP also maintains a terminal support tablewith some information regarding non-MTC device capability information,such as radio capabilities of the device.

With reference back to FIG. 1, in accordance with various embodiments,the mechanism via which a UE (e.g., UEs 102) determines MTC capabilityinformation and automatically provides the MTC capability information tothe DCCS is based on a dedicated STK or CAT application provided on aSIM card or UICC, respectively, of the UE. This application is referredto herein as the “capability information application.” The terms SIMcard and UICC are used herein interchangeably to refer to an integratedcircuit card that provides same or similar features and functionalitieswhen employed in association with a UE that is configured to operateusing a wireless communication network. In general, the SIM card and theUICC contain unique information that identifies a UE to a wirelesscommunication network with which the SIM card or UICC is registered andenables the UE to operate using the wireless communication network. Inaddition to storing secure device information, both the SIM card andUICC have applications (e.g., STK and CAT applications, respectively)that define how the SIM or UICC should interact directly with theoutside world. The STK and CAT applications can initiate commandsindependently of the UE on the network. This enables the SIM/UICC tobuild up an interactive exchange between a network application and theend user and access, or control access to the network. The UICC isconsidered a next generation SIM card and has applications beyond GSMnetworks.

In one or more embodiments, the capability information applicationprovided on the SIM/UICC of a UE (e.g., UEs 102) is configured toidentify or determine defined MTC capabilities of the UE in response tostart-up of the UE, a device reset, a new power cycle or another definedevent. In various implementations, the defined MTC capabilities caninclude a defined MTC device type or category of the UE. For example, in3GGP cellular systems, categories are used to define general UEperformance characteristics such as maximum supported data rate inuplink and downlink data channels, and to what extent differentmulti-antenna capabilities and modulation schemes are supported. 3GPPalso uses the concept of “Releases” to refer to a stable set ofspecifications, which can be used for implementation of features at agiven point of time. In Release 12, UE categories range from Category 0(Cat-0) up to Cat-13. With a Cat-1 UE, it is possible to achieve 10mega-bytes per second (Mbps) downlink and 5 Mbps uplink channel datarates. No multiple-input multiple output (MIMO) is supported but the UEshould still have 2 receiver antennas. Release 13 includes further UECategories including at least the so-called “Cat-M1” and “Cat-M2”intended for “Internet of things” (IoT) MTC devices. Cat-M1 and Cat-M2respectively have complexity reductions relative to Cat-0 and Cat-1. Forexample, Cat-M1 UEs have up to about 75-80% complexity reductionscompared to Cat-1 devices and Cat-M2 devices have up to about 90%complexity reductions compared to Cat-1 devices. One major differencebetween Cat-1 UEs and the “machine” (M) categories M1 and M2 relative toCat-1 UEs is the ability to implement the UE transmitter and receiverparts with reduced bandwidth compared to normal LTE UEs operating with20 MHz bandwidth.

The defined MTC capabilities can further include defined MTC operatingfeatures supported and/or not supported by the UE. For example, twopotential MTC operating features that may be supported by a UE (e.g.,UEs 102), respectively referred as extended discontinuous reception(eDRX) and power saving mode (PSM), are features that enable UEs to havevery long battery lifetimes, 10 years or more. The eDRX feature meansthe UE is configured to employ extended DRX cycles and provides the UEwith longer sleeping periods between reading paging or control channels.The PSM feature allows the UE to save power when there is no frequentneed for other devices to communicate with the UE. In addition to eDRXand PSM, other potential MTC operating features that can be supported bya UE can include but are not limited to: Non-Access Stratum (NAS)Signaling Priority support, Minimum Periodic Search Timer support,Extended Access Barring support, Timer T3245 support, Override NASSignaling Low Priority support, Override Extended Access Barringsupport, SM-Retry Wait Time support, Delay Tolerant Access support,Coverage Enhancement Mode A (CEModeA) support, Coverage Enhancement ModeB (CEModeB) support, Idle Mode Extended Discontinuous Reception (eDRx)support, Connected Mode Extended Discontinuous Reception (eDRx) support,Positioning support, and Single Cell-Point to Multipoint Transmission(SC-PTM) support.

Accordingly, in response to start-up of a UE (or another defined event),the capability information application can be configured to determine anMTC category of the UE and what MTC operating features the UE supports(and/or does not support). The capability information application canfurther generate MTC capability information that identifies the specificMTC device type or category of the UE and the MTC operating featuresthat are supported and/or not supported by the UE. For example, thecapability information application can create a data file withinformation identifying the MTC device category and operating features.In some embodiments, in association with generation of the MTCcapability information, the capability information application can beconfigured to store the MTC capability information in a data structurethat is stored on the device SIM/UICC. In various implementations, thisdata structure is referred to as the “terminal support table.” Forexample, in response to start-up of the UE, the capability informationapplication can interface with the UE and identify or determine thedefined MTC capabilities of the UE (e.g., the MTC category and MTCoperating features). The capability information application can furtherwrite the device MTC capability information to the terminal supporttable. The capability information application (or another reportingapplication stored on the SIM/UICC) can further be configured to send ordirect the UE to send (e.g., using a transmitter of the UE) the MTCcapability information to the DCCS using an OTA message sent via a M2Swireless communication link established between the UE and a networknode (e.g., network node 104).

FIG. 3 is an illustration of an example UE 300 that facilitates devicebased network notification of device MTC features in accordance withvarious aspects and embodiments of the subject disclosure. In variousembodiments, the one or more of the UEs 102 of system 100 can be orinclude UE 300, and vice versa. Repetitive description of like elementsemployed in respective embodiments is omitted for sake of brevity.

The UE can include memory 302 configured to store computer executablecomponents and instructions. For example, in various embodiments, thesecomputer executable components and instructions can include one or moreMTC software components 304. The one or more MTC software components 304can include components or instructions that control one or more definedMTC related operating parameters of the UE, such as eDRX, PSM and otherpossible MTC operating features. The UE 300 can also include a processor306 to facilitate operation of the instructions (e.g., the computerexecutable components and instructions) by the UE (e.g., the one or moreMTC software components). The UE 300 further includes a communicationcomponent 308, a power source 310 and an IC card 314 and a device bus312. The device bus 312 can couple the various components of the UEincluding, but not limited to, the memory 302, the processor 306, thecommunication component 308, the power source 310, and the IC card 314.Examples of said processor 306 and memory 302, as well as other suitablecomputer or computing-based elements that can be employed by the UE, canbe found with reference to FIG. 9.

The communication component 308 can facilitate wireless communicationbetween the UE and other devices, such as between the UE 300 and otherUEs via an M2M link and/or between the UE 300 and a wirelesscommunication system network node (e.g., network node 104). Thecommunication component 308 can be or include hardware (e.g., a centralprocessing unit (CPU), a transmitter, a receiver, a transceiver, adecoder), software (e.g., a set of threads, a set of processes, softwarein execution) or a combination of hardware and software that facilitatesone or more of the various types of wireless communications describedherein. The power source 310 can provide power to the various electricalcomponents of the UE 300 to facilitate operation thereof (e.g., theprocessor 306, the communication component 308, the IC card 314, etc.).The power source 310 can include, but is not limited to, a battery, acapacitor, a charge pump, a mechanically derived power source (e.g.,microelectromechanical systems (MEMs) device), or an inductioncomponent.

The IC card 314 can include a fixed or removable integrated circuitchip. The IC card can include memory 316 that stores information andcomputer executable components or instructions (e.g., the capabilityinformation application 318). In some embodiments, the IC card 314 caninclude a micro-processor 330 to facilitate operation of at least somethe instructions stored in the memory 316 (e.g., the capabilityinformation application 318). In other embodiments, the UE can beconfigured to employ processor 306 to execute the instructions stored inmemory 316. For example, in some embodiments, the IC card 314 is a SIMcard or a UICC that stores network subscriber data 328 that includesnetwork-specific information used to authenticate and identify asubscriber on a wireless communication network (e.g., system 100). Forexample, the network subscriber data can 328 can include but is notlimited to, a unique serial number (ICCID) associated with thesubscriber, an IMEI number associated with the subscriber, securityauthentication and ciphering information, temporary information relatedto the local network, a list of the services the subscriber has accessto, and password information (e.g., a personal identification number(PIN) for ordinary use, and a personal unblocking code (PUK) for PINunlocking. In addition, the IC card 314 can include one or more STK orCAT applications that consist of a set of commands programmed into theSIM/UICC card, which define how the SIM/UICC should interact directlywith the outside world and initiates commands independently of the UEand the network. This enables the SIM/UICC to build up an interactiveexchange between a network application and the end user and access orcontrol access to the network. In one or more embodiments, at least oneof these STK or CAT applications is a capability information application318.

In accordance with various embodiments, the capability informationapplication 318 can be configured to determine information regarding MTCcapabilities of the UE 300 and automatically provide informationidentifying the MTC capabilities of the UE to the DCCS (e.g., DCCS 220)of the wireless communication network that facilitates various wirelesscommunication services of the UE 300. In one or more embodiments, thecapability information application 318 can include capabilityidentification component 320, capability recording component 322, andcapability reporting component 324. The capability identificationcomponent 320 can be configured to identify or determine defined MTCcapabilities of the UE in response to start-up of the UE, a devicereset, a new power cycle or another defined event. In particular, inresponse to start-up, (a reset, a new power cycle, etc.), of the UE 300,the capability identification component 320 can be configured to accessinformation stored in memory 302 and/or memory 316 regarding featuresand functionalities of the UE to determine or identify defined MTCdevice capabilities of the UE 300. As previously described, thesedefined MTC capabilities can include a defined MTC device type orcategory of the UE (e.g., Cat-M1, Cat-M2, Cat-0, Cat-1, etc). In someembodiments, the MTC device type or category can relate to an uplinkthroughput of the UE and a downlink throughput of the UE. The definedMTC capabilities can also include defined MTC operating featuressupported (or not supported) by the UE.

For example, FIG. 4 provides a chart 400 illustrating example MTC devicetype/category information in accordance with various aspects andembodiments of the subject disclosure. As shown in chart 400, the MTCdevice type/category can include a device type/category supported on thedownlink and a device type/category supported on the uplink downlink. Asingle Hex value can be employed to represent the specificdownlink/uplink device type/category combination. For example, a UE canhave the same device type/category on the downlink and the uplink orhave a different downlink category relative to the uplink category. Insome embodiments, the device type/category relates to at least in part,a data throughput or speed. Chart 400 demonstrate some example devicedownlink/uplink category combinations associated with the devicetypes/categories defined by in the 3GGP Releases 12 and 13 (e.g., M1,M2, and Cat-0 through Cat-13). However, it should be appreciated thatthe potential device types/categories shown in chart 400 are merelyexemplary and other device types/categories (e.g., associated with 4GGPReleases, 5GGP Releases and beyond) are envisioned.

FIG. 5 presents example MTC device operating features in accordance withvarious aspects and embodiments of the subject disclosure. In one ormore embodiments, the UE MTC operating feature information can beassociated with one or more data bytes, wherein respective bits (e.g.,bits b1-b8) of the data bytes represent a defined MTC operating feature.In the embodiment shown, these defined MTC operating features include:NAS Signaling Priority, Minimum Periodic Search Time, Extended AccessBarring, Timer T3245, Override NAS Signaling Low Priority, OverrideExtended Access Barring, SM-Retry Wait Time, Delay Tolerant Access,Coverage Enhancement Mode A (CEModeA), Coverage Enhancement Mode B(CEModeB), Idle Mode Extended Discontinuous Reception (eDRx, ConnectedMode Extended Discontinuous Reception (eDRx), Positioning, and SingleCell-Point to Multipoint Transmission (SC-PTM). According to theseembodiments, a first value (e.g., a 0) for a bit can indicate the UEdoes not support that MTC operating parameter and a second value (e.g.,a 1) for the bit can indicate the UE supports that MTC operationparameter. For example, in the embodiment shown, three 8 bit bytes havebeen designated to represent MTC device operating parameters. Thespecific MTC operating parameters represented by the third byte have notyet been defined, as indicated by the term RFU associated with each bit,which represents “reserved for future use.” According to this example,the third byte has been reserved to represent future MTC operatingfeature that may be implemented over time.

With reference back to FIG. 3, in response to start-up of the UE, (adevice rest, a new power cycle, or another defined event), thecapability identification component 320 can be configured identify ordetermine (e.g., based on information stored in memory 302 and/or memory316) an MTC category of the UE 300 and what MTC operating features of aset of defined potential MTC operating features the UE supports (and/ordoes not support). The capability recording component 322 can furthergenerate MTC capability information that identifies the specific MTCdevice type/category of the UE and the MTC operating features that aresupported and/or not supported by the UE. For example, the capabilityrecording component 322 can be configured to generate a data file withinformation identifying the MTC device category and operating features.In some embodiments, the capability recording component 322 can use asingle data byte to represent the MTC device type/category. For example,in accordance with the examples shown in chart 400 of FIG. 4, becausethe device type/category can only be one possible Hex value of a set ofHex values, the device type can be defined by a single unique 8 bitbyte. In other embodiments, the capability recording component 322 canuse two (e.g., one for the downlink category and one of the uplinkcategory) or more bytes to represent the UE MTC type/category. Thecapability recording component 322 can also be configured to use two ormore bytes to represent the different MTC operating features supported(and not supported) by the UE (e.g., as discussed with reference to FIG.5).

In some embodiments, in association with generation of the MTCcapability information, the capability recording component 322 can beconfigured to store the MTC capability information in a data structurethat is stored in the memory 316 of on the IC card 314. As noted above,in various implementations, this data structure is referred to as the“terminal support table.” For example, in response to start-up of theUE, the capability identification component 320 can interface with theUE and identify or determine the defined MTC capabilities of the UE(e.g., the MTC category and MTC operating features). The capabilityrecording component 322 can further write the device MTC capabilityinformation to the terminal support table 326.

The capability information application 318 can further includecapability reporting component 324 to facilitate providing UE MTCcapability information to the DCCS. In other embodiments, (not shown)the capability reporting component 324 can be associated with adifferent application provided in memory 316 or memory 302. In one ormore embodiments, the capability reporting component 324 can beconfigured to send or direct the UE to send (e.g., using communicationcomponent 308) the MTC capability information to the DCCS using an OTAmessage sent via a M2S wireless communication link established betweenthe UE 300 and a network node (e.g., network node 104). In one or moreimplementations, the OTA message can include a mobile originated (MO)short message service (SMS) class 2 message. SMS message classesidentify the importance of the message and the location where it shouldbe stored. There are four SMS message classes defined by the 3GGPstandard, class 0, class 1, claim 2 and class 3. A class 2 is phase2-specific and carries SIM/UICC data. With a MO-SMS class 2 message, thedata is to be successfully transferred prior to sending acknowledgmentto the SMS service center (SC). An error message is sent to the SC ifthis transmission is not possible.

In some embodiments, the capability reporting component 324 can beconfigured to automatically cause the UE 300 to send the MTC capabilityinformation (e.g., information identifying the UE MTC type/category andthe MTC operating parameters supported/not supported by the UE) to theDCCS in response to identification/determination of the information bythe capability identification component 320. With these embodiments,each time the UE 300 powers-up (is reset, or another defined eventoccurs), the UE will identify/determine MTC device capabilityinformation and send the MTC device capability information to the DCCS.In other embodiments, capability reporting component 324 can beconfigured to only send the DCCS UE MTC capability information that wasnot previously provided to the DCCS. For example, in association withstart-up of the UE 300, the capability reporting component 324 candetermine whether a specific data structure in memory 316 (e.g., theterminal support table 326) includes any MTC device capabilityinformation that was not previously included in the data structure priorto the start-up. The capability reporting component 324 can further beconfigured to send an OTA message to the DCCS including the UE MTCcapability information included in the data structure in response to adetermination that the UE MTC capability information was not included inthe data structure prior to the start-up. Accordingly, after thecapability reporting component 324 provides the DCCS with UE MTCcapability information for the first time, the capability reportingcomponent 324 will not provide the DCCS with UE MTC capabilityinformation unless the UE is updated with new MTC capability informationor the original UE MTC capability information written in the terminalsupport table is removed (e.g., in response to a device master reset).

In view of the example system(s) described above, example method(s) thatcan be implemented in accordance with the disclosed subject matter canbe better appreciated with reference to flowcharts in FIGS. 6-8. Forpurposes of simplicity of explanation, example methods disclosed hereinare presented and described as a series of acts; however, it is to beunderstood and appreciated that the claimed subject matter is notlimited by the order of acts, as some acts may occur in different ordersand/or concurrently with other acts from that shown and describedherein. For example, one or more example methods disclosed herein couldalternatively be represented as a series of interrelated states orevents, such as in a state diagram. Moreover, interaction diagram(s) mayrepresent methods in accordance with the disclosed subject matter whendisparate entities enact disparate portions of the methods. Furthermore,not all illustrated acts may be required to implement a describedexample method in accordance with the subject specification. Furtheryet, two or more of the disclosed example methods can be implemented incombination with each other, to accomplish one or more aspects hereindescribed. It should be further appreciated that the example methodsdisclosed throughout the subject specification are capable of beingstored on an article of manufacture (e.g., a computer-readable medium)to allow transporting and transferring such methods to computers forexecution, and thus implementation, by a processor or for storage in amemory.

FIG. 6 illustrates an example method 600 that facilitates device basednetwork notification of device supported MTC features in accordance withvarious aspects and embodiments of the subject disclosure. Repetitivedescription of like elements employed in respective embodiments isomitted for sake of brevity.

At 602, a device comprising a processor (e.g., a UE 102, UE 300 or thelike), identifies MTC related parameters of the device using a SIMapplication (e.g., capability information application 318) stored on aSIM card (e.g., IC card 314) of the device. At 604, the devicegenerates, using the SIM application, MTC information that identifiesthe MTC related parameters of the device based on the identifying theMTC related parameters. At 606, the device sends the MTC parameterinformation to a network server device (e.g., the DCCS 220) of awireless communication network based on the generating.

FIG. 7 illustrates another example method 700 that facilitates devicebased network notification of device supported MTC features inaccordance with various aspects and embodiments of the subjectdisclosure. Repetitive description of like elements employed inrespective embodiments is omitted for sake of brevity.

At 702, an IC card device comprising a processor (e.g., IC card 314)determines MTC related parameters of a device operatively coupled to theIC card (e.g., UE 300). At 704, the IC card device, generates MTCparameter information that identifies the MTC related parameters of thedevice based on the determining. At 706, the directing, by the IC carddevice directs, based on the generating, a transmitter of the device(e.g., a transmitter of the communication component 308) to send the MTCparameter information to a network server device of a wirelesscommunication network (e.g., DCCS 220) using a wireless communicationlink established between the device and an access point device (e.g.,network node 104) of the wireless communication network.

FIG. 8 illustrates another example method 800 that facilitates devicebased network notification of device supported MTC features inaccordance with various aspects and embodiments of the subjectdisclosure. Repetitive description of like elements employed inrespective embodiments is omitted for sake of brevity.

At 802, in response to start-up of a device comprising a processor(e.g., a UE 102, UE 300 and the like), the device determines, using anapplication provided on a UICC of the device (e.g., capabilityinformation application 318), a MTC related category of the device andMTC operating features supported by the device (e.g., using capabilityidentification component 320). At 804, the device generates, using theapplication, MTC related category and the MTC operating featuressupported by the device (e.g., using capability recording component322). At 806, the device stores (e.g., using the capability recordingcomponent 322), the MTC capability information in a data structure(e.g., the terminal support table 326) in a memory of the UICC (e.g.,memory 316). At 808, the device sends the MTC capability information toa network server device (e.g., DCCS 220) of a wireless communicationnetwork in response to a determination that the MTC capabilityinformation was not previously stored in the data structure prior to thestart-up.

FIG. 9 is a schematic block diagram of a computing environment 900 withwhich the disclosed subject matter can interact. The system 900comprises one or more remote component(s) 910. The remote component(s)910 can be hardware and/or software (e.g., threads, processes, computingdevices). In some embodiments, remote component(s) 910 can compriseservers, personal servers, wireless telecommunication network devices,RAN device(s), etc. As an example, remote component(s) 910 can benetwork node 104, network devices 108, 200 and the like. The system 900also comprises one or more local component(s) 920. The localcomponent(s) 920 can be hardware and/or software (e.g., threads,processes, computing devices). In some embodiments, local component(s)920 can comprise, for example, UEs 102, UE 300, and the like.

One possible communication between a remote component(s) 910 and a localcomponent(s) 920 can be in the form of a data packet adapted to betransmitted between two or more computer processes. Another possiblecommunication between a remote component(s) 910 and a local component(s)920 can be in the form of circuit-switched data adapted to betransmitted between two or more computer processes in radio time slots.The system 900 comprises a communication framework 940 that can beemployed to facilitate communications between the remote component(s)910 and the local component(s) 920, and can comprise an air interface,e.g., Uu interface of a UMTS network, via an LTE network, etc. Remotecomponent(s) 910 can be operably connected to one or more remote datastore(s) 950, such as a hard drive, solid state drive, SIM card, devicememory, etc., that can be employed to store information on the remotecomponent(s) 910 side of communication framework 940. Similarly, localcomponent(s) 920 can be operably connected to one or more local datastore(s) 930, that can be employed to store information on the localcomponent(s) 920 side of communication framework 940.

In order to provide a context for the various aspects of the disclosedsubject matter, FIG. 10, and the following discussion, are intended toprovide a brief, general description of a suitable environment in whichthe various aspects of the disclosed subject matter can be implemented.While the subject matter has been described above in the general contextof computer-executable instructions of a computer program that runs on acomputer and/or computers, those skilled in the art will recognize thatthe disclosed subject matter also can be implemented in combination withother program modules. Generally, program modules comprise routines,programs, components, data structures, etc. that performs particulartasks and/or implement particular abstract data types.

In the subject specification, terms such as “store,” “storage,” “datastore,” data storage,” “database,” and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It is noted that thememory components described herein can be either volatile memory ornonvolatile memory, or can comprise both volatile and nonvolatilememory, by way of illustration, and not limitation, volatile memory 1020(see below), non-volatile memory 1022 (see below), disk storage 1024(see below), and memory storage 1046 (see below). Further, nonvolatilememory can be included in read only memory, programmable read onlymemory, electrically programmable read only memory, electricallyerasable read only memory, or flash memory. Volatile memory can compriserandom access memory, which acts as external cache memory. By way ofillustration and not limitation, random access memory is available inmany forms such as synchronous random access memory, dynamic randomaccess memory, synchronous dynamic random access memory, double datarate synchronous dynamic random access memory, enhanced synchronousdynamic random access memory, Synchlink dynamic random access memory,and direct Rambus random access memory. Additionally, the disclosedmemory components of systems or methods herein are intended to comprise,without being limited to comprising, these and any other suitable typesof memory.

Moreover, it is noted that the disclosed subject matter can be practicedwith other computer system configurations, comprising single-processoror multiprocessor computer systems, mini-computing devices, mainframecomputers, as well as personal computers, hand-held computing devices(e.g., personal digital assistant, phone, watch, tablet computers,notebook computers, . . . ), microprocessor-based or programmableconsumer or industrial electronics, and the like. The illustratedaspects can also be practiced in distributed computing environmentswhere tasks are performed by remote processing devices that are linkedthrough a communications network; however, some if not all aspects ofthe subject disclosure can be practiced on stand-alone computers. In adistributed computing environment, program modules can be located inboth local and remote memory storage devices.

FIG. 10 illustrates a block diagram of a computing system 1000 operableto execute the disclosed systems and methods in accordance with anembodiment. Computer 1012, which can be, for example, a UE (e.g., UE 102and 300), a network node (e.g., network node 104), comprises aprocessing unit 1014, a system memory 1016, and a system bus 1018.System bus 1018 couples system components comprising, but not limitedto, system memory 1016 to processing unit 1014. Processing unit 1014 canbe any of various available processors. Dual microprocessors and othermultiprocessor architectures also can be employed as processing unit1014.

System bus 1018 can be any of several types of bus structure(s)comprising a memory bus or a memory controller, a peripheral bus or anexternal bus, and/or a local bus using any variety of available busarchitectures comprising, but not limited to, industrial standardarchitecture, micro-channel architecture, extended industrial standardarchitecture, intelligent drive electronics, video electronics standardsassociation local bus, peripheral component interconnect, card bus,universal serial bus, advanced graphics port, personal computer memorycard international association bus, Firewire (Institute of Electricaland Electronics Engineers 11104), and small computer systems interface.

System memory 1016 can comprise volatile memory 1020 and nonvolatilememory 1022. A basic input/output system, containing routines totransfer information between elements within computer 1012, such asduring start-up, can be stored in nonvolatile memory 1022. By way ofillustration, and not limitation, nonvolatile memory 1022 can compriseread only memory, programmable read only memory, electricallyprogrammable read only memory, electrically erasable read only memory,or flash memory. Volatile memory 1020 comprises read only memory, whichacts as external cache memory. By way of illustration and notlimitation, read only memory is available in many forms such assynchronous random access memory, dynamic read only memory, synchronousdynamic read only memory, double data rate synchronous dynamic read onlymemory, enhanced synchronous dynamic read only memory, Synchlink dynamicread only memory, Rambus direct read only memory, direct Rambus dynamicread only memory, and Rambus dynamic read only memory.

Computer 1012 can also comprise removable/non-removable,volatile/non-volatile computer storage media. FIG. 10 illustrates, forexample, disk storage 1024. Disk storage 1024 comprises, but is notlimited to, devices like a magnetic disk drive, floppy disk drive, tapedrive, flash memory card, or memory stick. In addition, disk storage1024 can comprise storage media separately or in combination with otherstorage media comprising, but not limited to, an optical disk drive suchas a compact disk read only memory device, compact disk recordabledrive, compact disk rewritable drive or a digital versatile disk readonly memory. To facilitate connection of the disk storage devices 1024to system bus 1018, a removable or non-removable interface is typicallyused, such as interface 1026.

Computing devices typically comprise a variety of media, which cancomprise computer-readable storage media or communications media, whichtwo terms are used herein differently from one another as follows.

Computer-readable storage media can be any available storage media thatcan be accessed by the computer and comprises both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media cancomprise, but are not limited to, read only memory, programmable readonly memory, electrically programmable read only memory, electricallyerasable read only memory, flash memory or other memory technology,compact disk read only memory, digital versatile disk or other opticaldisk storage, magnetic cassettes, magnetic tape, magnetic disk storageor other magnetic storage devices, or other tangible media which can beused to store desired information. In this regard, the term “tangible”herein as may be applied to storage, memory or computer-readable media,is to be understood to exclude only propagating intangible signals perse as a modifier and does not relinquish coverage of all standardstorage, memory or computer-readable media that are not only propagatingintangible signals per se. In an aspect, tangible media can comprisenon-transitory media wherein the term “non-transitory” herein as may beapplied to storage, memory or computer-readable media, is to beunderstood to exclude only propagating transitory signals per se as amodifier and does not relinquish coverage of all standard storage,memory or computer-readable media that are not only propagatingtransitory signals per se. Computer-readable storage media can beaccessed by one or more local or remote computing devices, e.g., viaaccess requests, queries or other data retrieval protocols, for avariety of operations with respect to the information stored by themedium. As such, for example, a computer-readable medium can compriseexecutable instructions stored thereon that, in response to execution,cause a system comprising a processor to perform operations, comprisinggenerating an RRC connection release message further comprisingalterative band channel data.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and comprises any informationdelivery or transport media. The term “modulated data signal” or signalsrefers to a signal that has one or more of its characteristics set orchanged in such a manner as to encode information in one or moresignals. By way of example, and not limitation, communication mediacomprise wired media, such as a wired network or direct-wiredconnection, and wireless media such as acoustic, RF, infrared and otherwireless media.

It can be noted that FIG. 10 describes software that acts as anintermediary between users and computer resources described in suitableoperating environment 1000. Such software comprises an operating system1028. Operating system 1028, which can be stored on disk storage 1024,acts to control and allocate resources of computer system 1012. Systemapplications 1030 take advantage of the management of resources byoperating system 1028 through program modules 1032 and program data 1034stored either in system memory 1016 or on disk storage 1024. It is to benoted that the disclosed subject matter can be implemented with variousoperating systems or combinations of operating systems.

A user can enter commands or information into computer 1012 throughinput device(s) 1036. In some embodiments, a user interface can allowentry of user preference information, etc., and can be embodied in atouch sensitive display panel, a mouse/pointer input to a graphical userinterface (GUI), a command line controlled interface, etc., allowing auser to interact with computer 1012. Input devices 1036 comprise, butare not limited to, a pointing device such as a mouse, trackball,stylus, touch pad, keyboard, microphone, joystick, game pad, satellitedish, scanner, TV tuner card, digital camera, digital video camera, webcamera, cell phone, smartphone, tablet computer, etc. These and otherinput devices connect to processing unit 1014 through system bus 1018 byway of interface port(s) 1038. Interface port(s) 1038 comprise, forexample, a serial port, a parallel port, a game port, a universal serialbus, an infrared port, a Bluetooth port, an IP port, or a logical portassociated with a wireless service, etc. Output device(s) 1040 use someof the same type of ports as input device(s) 1036.

Thus, for example, a universal serial busport can be used to provideinput to computer 1012 and to output information from computer 1012 toan output device 1040. Output adapter 1042 is provided to illustratethat there are some output devices 1040 like monitors, speakers, andprinters, among other output devices 1040, which use special adapters.Output adapters 1042 comprise, by way of illustration and notlimitation, video and sound cards that provide means of connectionbetween output device 1040 and system bus 1018. It should be noted thatother devices and/or systems of devices provide both input and outputcapabilities such as remote computer(s) 1044.

Computer 1012 can operate in a networked environment using logicalconnections to one or more remote computers, such as remote computer(s)1044. Remote computer(s) 1044 can be a personal computer, a server, arouter, a network PC, cloud storage, a cloud service, code executing ina cloud-computing environment, a workstation, a microprocessor basedappliance, a peer device, or other common network node and the like, andtypically comprises many or all of the elements described relative tocomputer 1012. A cloud computing environment, the cloud, or othersimilar terms can refer to computing that can share processing resourcesand data to one or more computer and/or other device(s) on an as neededbasis to enable access to a shared pool of configurable computingresources that can be provisioned and released readily. Cloud computingand storage solutions can storing and/or processing data in third-partydata centers which can leverage an economy of scale and can viewaccessing computing resources via a cloud service in a manner similar toa subscribing to an electric utility to access electrical energy, atelephone utility to access telephonic services, etc.

For purposes of brevity, only a memory storage device 1046 isillustrated with remote computer(s) 1044. Remote computer(s) 1044 islogically connected to computer 1012 through a network interface 1048and then physically connected by way of communication connection 1050.Network interface 1048 encompasses wire and/or wireless communicationnetworks such as local area networks and wide area networks. Local areanetwork technologies comprise fiber distributed data interface, copperdistributed data interface, Ethernet, Token Ring and the like. Wide areanetwork technologies comprise, but are not limited to, point-to-pointlinks, circuit-switching networks like integrated services digitalnetworks and variations thereon, packet switching networks, and digitalsubscriber lines. As noted below, wireless technologies may be used inaddition to or in place of the foregoing.

Communication connection(s) 1050 refer(s) to hardware/software employedto connect network interface 1048 to bus 1018. While communicationconnection 1050 is shown for illustrative clarity inside computer 1012,it can also be external to computer 1012. The hardware/software forconnection to network interface 1048 can comprise, for example, internaland external technologies such as modems, comprising regular telephonegrade modems, cable modems and digital subscriber line modems,integrated services digital network adapters, and Ethernet cards.

The above description of illustrated embodiments of the subjectdisclosure, comprising what is described in the Abstract, is notintended to be exhaustive or to limit the disclosed embodiments to theprecise forms disclosed. While specific embodiments and examples aredescribed herein for illustrative purposes, various modifications arepossible that are considered within the scope of such embodiments andexamples, as those skilled in the relevant art can recognize.

In this regard, while the disclosed subject matter has been described inconnection with various embodiments and corresponding Figures, whereapplicable, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for performing the same, similar, alternative, or substitutefunction of the disclosed subject matter without deviating therefrom.Therefore, the disclosed subject matter should not be limited to anysingle embodiment described herein, but rather should be construed inbreadth and scope in accordance with the appended claims below.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit, a digital signalprocessor, a field programmable gate array, a programmable logiccontroller, a complex programmable logic device, a discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described herein. Processorscan exploit nano-scale architectures such as, but not limited to,molecular and quantum-dot based transistors, switches and gates, inorder to optimize space usage or enhance performance of user equipment.A processor may also be implemented as a combination of computingprocessing units.

As used in this application, the terms “component,” “system,”“platform,” “layer,” “selector,” “interface,” and the like are intendedto refer to a computer-related entity or an entity related to anoperational apparatus with one or more specific functionalities, whereinthe entity can be either hardware, a combination of hardware andsoftware, software, or software in execution. As an example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration and not limitation, both anapplication running on a server and the server can be a component. Oneor more components may reside within a process and/or thread ofexecution and a component may be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media having various datastructures stored thereon. The components may communicate via localand/or remote processes such as in accordance with a signal having oneor more data packets (e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems via the signal). Asanother example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry, which is operated by a software or firmwareapplication executed by a processor, wherein the processor can beinternal or external to the apparatus and executes at least a part ofthe software or firmware application. As yet another example, acomponent can be an apparatus that provides specific functionalitythrough electronic components without mechanical parts, the electroniccomponents can comprise a processor therein to execute software orfirmware that confers at least in part the functionality of theelectronic components.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form.

Further, the term “include” is intended to be employed as an open orinclusive term, rather than a closed or exclusive term. The term“include” can be substituted with the term “comprising” and is to betreated with similar scope, unless otherwise explicitly used otherwise.As an example, “a basket of fruit including an apple” is to be treatedwith the same breadth of scope as, “a basket of fruit comprising anapple.”

Moreover, terms like “user equipment (UE),” “mobile station,” “mobile,”subscriber station,” “subscriber equipment,” “access terminal,”“terminal,” “handset,” and similar terminology, refer to a wirelessdevice utilized by a subscriber or user of a wireless communicationservice to receive or convey data, control, voice, video, sound, gaming,or substantially any data-stream or signaling-stream. The foregoingterms are utilized interchangeably in the subject specification andrelated drawings. Likewise, the terms “access point,” “base station,”“Node B,” “evolved Node B,” “eNodeB,” “home Node B,” “home accesspoint,” and the like, are utilized interchangeably in the subjectapplication, and refer to a wireless network component or appliance thatserves and receives data, control, voice, video, sound, gaming, orsubstantially any data-stream or signaling-stream to and from a set ofsubscriber stations or provider enabled devices. Data and signalingstreams can comprise packetized or frame-based flows.

Additionally, the terms “core-network”, “core”, “core carrier network”,“carrier-side”, or similar terms can refer to components of atelecommunications network that typically provides some or all ofaggregation, authentication, call control and switching, charging,service invocation, or gateways. Aggregation can refer to the highestlevel of aggregation in a service provider network wherein the nextlevel in the hierarchy under the core nodes is the distribution networksand then the edge networks. UEs do not normally connect directly to thecore networks of a large service provider but can be routed to the coreby way of a switch or radio access network. Authentication can refer todeterminations regarding whether the user requesting a service from thetelecom network is authorized to do so within this network or not. Callcontrol and switching can refer determinations related to the futurecourse of a call stream across carrier equipment based on the callsignal processing. Charging can be related to the collation andprocessing of charging data generated by various network nodes. Twocommon types of charging mechanisms found in present day networks can beprepaid charging and postpaid charging. Service invocation can occurbased on some explicit action (e.g. call transfer) or implicitly (e.g.,call waiting). It is to be noted that service “execution” may or may notbe a core network functionality as third party network/nodes may takepart in actual service execution. A gateway can be present in the corenetwork to access other networks. Gateway functionality can be dependenton the type of the interface with another network.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,”“prosumer,” “agent,” and the like are employed interchangeablythroughout the subject specification, unless context warrants particulardistinction(s) among the terms. It should be appreciated that such termscan refer to human entities or automated components (e.g., supportedthrough artificial intelligence, as through a capacity to makeinferences based on complex mathematical formalisms), that can providesimulated vision, sound recognition and so forth.

Aspects, features, or advantages of the subject matter can be exploitedin substantially any, or any, wired, broadcast, wirelesstelecommunication, radio technology or network, or combinations thereof.Non-limiting examples of such technologies or networks comprisebroadcast technologies (e.g., sub-Hertz, extremely low frequency, verylow frequency, low frequency, medium frequency, high frequency, veryhigh frequency, ultra-high frequency, super-high frequency, terahertzbroadcasts, etc.); Ethernet; X.25; powerline-type networking, e.g.,Powerline audio video Ethernet, etc.; femtocell technology; Wi-Fi;worldwide interoperability for microwave access; enhanced general packetradio service; third generation partnership project, long termevolution; third generation partnership project universal mobiletelecommunications system; third generation partnership project 2, ultramobile broadband; high speed packet access; high speed downlink packetaccess; high speed uplink packet access; enhanced data rates for globalsystem for mobile communication evolution radio access network;universal mobile telecommunications system terrestrial radio accessnetwork; or long term evolution advanced.

The term “infer” or “inference” can generally refer to the process ofreasoning about, or inferring states of, the system, environment, user,and/or intent from a set of observations as captured via events and/ordata. Captured data and events can include user data, device data,environment data, data from sensors, sensor data, application data,implicit data, explicit data, etc. Inference, for example, can beemployed to identify a specific context or action, or can generate aprobability distribution over states of interest based on aconsideration of data and events. Inference can also refer to techniquesemployed for composing higher-level events from a set of events and/ordata. Such inference results in the construction of new events oractions from a set of observed events and/or stored event data, whetherthe events, in some instances, can be correlated in close temporalproximity, and whether the events and data come from one or severalevent and data sources. Various classification schemes and/or systems(e.g., support vector machines, neural networks, expert systems,Bayesian belief networks, fuzzy logic, and data fusion engines) can beemployed in connection with performing automatic and/or inferred actionin connection with the disclosed subject matter.

What has been described above includes examples of systems and methodsillustrative of the disclosed subject matter. It is, of course, notpossible to describe every combination of components or methods herein.One of ordinary skill in the art may recognize that many furthercombinations and permutations of the claimed subject matter arepossible. Furthermore, to the extent that the terms “includes,” “has,”“possesses,” and the like are used in the detailed description, claims,appendices and drawings such terms are intended to be inclusive in amanner similar to the term “comprising” as “comprising” is interpretedwhen employed as a transitional word in a claim.

What is claimed is:
 1. A method, comprising: initiating, by a subscriberidentity module card operatively coupled to a processor, an applicationof the subscriber identity module card, wherein the subscriber identitymodule card is further operatively coupled to a machine-typecommunication device; based on the initiating, determining, by thesubscriber identity module card using the application, whether aterminal support data structure of the subscriber identity module cardcomprises parameter information defining machine-type communicationparameters of the machine-type communication device; based on adetermination that the parameter information is excluded from theterminal support data structure, updating, by the subscriber identitymodule card using the application, the terminal support data structureto include the parameter information; and based on the updating,sending, by the subscriber identity module card using the application,the terminal support data structure to a network device of a wirelesscommunication network to facilitate provisioning machine-typecommunication services for the machine-type communication device via thewireless communication network based on the parameter information. 2.The method of claim 1, further comprising: facilitating establishing, bythe subscriber identity module card using the application, acommunication link between the subscriber identity module card and anaccess point device of the wireless communication network, wherein thesending comprises sending the parameter information to the networkdevice using the communication link.
 3. The method of claim 1, whereinthe network device facilitates the provisioning by forwarding theparameter information to additional network devices of the wirelesscommunication network other than the network device.
 4. The method ofclaim 1, wherein the network device further facilitates charging a useraccount associated with the machine-type communication device for theprovisioning of the machine-type communication services based onreceiving the parameter information.
 5. The method of claim 1, whereinthe machine-type communication parameters comprise a defined category ofthe machine-type communication device.
 6. The method of claim 5, whereinthe defined category relates to an uplink throughput of the machine-typecommunication device and a downlink throughput of the machine-typecommunication device.
 7. The method of claim 5, wherein the updatingcomprises, writing, by the subscriber identity module card using theapplication, the parameter information to the terminal support datastructure using a single data byte that represents the defined categoryof the machine-type communication device.
 8. The method of claim 1,wherein the machine-type communication parameters comprise definedmachine-type communication features supported by the machine-typecommunication device.
 9. The method of claim 8, wherein the updatingcomprises, writing, by the subscriber identity module card using theapplication, the parameter information to the terminal support datastructure using data bytes that represent the defined machine-typecommunication features supported by the machine-type communicationdevice, wherein each bit of the bytes represents a defined machine-typecommunication feature, and wherein a first bit value for each bitindicates the machine-type communication supports the definedmachine-type communication feature and a second bit value for each bitindicates the machine-type communication device does not support thedefined machine-type communication feature.
 10. The method of claim 1,wherein the initiating is responsive to a start-up operation of themachine-type communication device.
 11. The method of claim 1, whereinthe sending comprises sending the terminal support data structure to thenetwork device using a short message service class 2 message.
 12. Adevice, comprising: a transmitter; and a subscriber identity module cardcomprising: a processor, and a memory that stores executableinstructions that, wherein the processor executes the executableinstructions to perform operations, comprising: initiating a toolkitapplication of the subscriber identity module card; based on theinitiating, determining, using the toolkit application, whether aterminal support table file of the subscriber identity module cardcomprises parameter information defining machine-type communicationrelated parameters of the device; based on a determination that theparameter information is excluded from the terminal support table file,updating the terminal support table file using the toolkit applicationto include the parameter information; and directing, based on theupdating, the transmitter to send the terminal support table file to anetwork server device of a wireless communication network via acommunication link between the device and an access point device of thewireless communication network to enable provisioning machine-typecommunication services for the device via the wireless communicationnetwork based the parameter information.
 13. The device of claim 12,wherein the network server device is configured to enable theprovisioning by forwarding the parameter information to additionalnetwork server devices of the wireless communication network other thanthe network server device.
 14. The device of claim 12, wherein thedevice comprises a machine-type communication device and themachine-type communication related parameters comprise a definedcategory of the machine-type communication device.
 15. The device ofclaim 12, wherein the machine-type communication related parameterscomprise defined machine-type communication features supported by thedevice.
 16. The device of claim 14, wherein the defined category relatesto an uplink throughput of the device and a downlink throughput of thedevice.
 17. The device of claim 14, wherein the updating comprises,writing, using the toolkit application, the parameter information to theterminal support table file using a single data byte that represents thedefined category of the device.
 18. The device of claim 15, wherein theupdating comprises, writing, using the toolkit application, theparameter information to the terminal support table file using databytes that represent the defined machine-type communication featuressupported by the device, wherein each bit of the bytes represents adefined machine-type communication feature, and wherein a first bitvalue for each bit indicates the machine-type communication supports thedefined machine-type communication feature and a second bit value foreach bit indicates the machine-type communication device does notsupport the defined machine-type communication feature.
 19. Anon-transitory machine-readable storage medium, comprising executableinstructions that, when executed by a processor associated with asubscriber identity module card, facilitate performance of operations,comprising: initiating an application of the subscriber identity modulecard, wherein the subscriber identity module card is further operativelycoupled to a machine-type communication device; based on the initiating,determining, using the application, that a designated file stored on thesubscriber identity module card does not include parameter informationthat identifies machine-type communication related parameters of themachine-type communication device; based on the determining, updatingthe designated file using the application to include the parameterinformation; and based on the updating, sending the parameterinformation to a network device of a wireless communication network tofacilitate provisioning machine-type communication services for themachine-type communication device via network devices of the wirelesscommunication network based on the parameter information, wherein thenetwork devices comprise the network device.
 20. The non-transitorymachine-readable storage medium of claim 19, wherein the machine-typecommunication related parameters comprise a defined category of themachine-type communication device and defined machine-type communicationfeatures supported by the machine-type communication device.